Use AI to model just a single section#2591
Merged
robertbrignull merged 1 commit intomainfrom Jul 7, 2023
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hooks up the "Model with AI" in each collapsible section to work on just methods from that model. Follows a very similar approach to the "save" button. This thankfully is quite easy since we pass all the data back to the extension host, so we can just send only the data for that model. From then on the extension host sends back some modelled methods and it all works the same as it did before.
The old "Generate using LLM" in the header still works on everything. This button will be removed at a later date once we've finished redesigning the collapsible sections.
Note: the "unsaved" label is a little broken and doesn't update correctly when modelling with AI. It's already broken before this change too so so my rough plan was to go forward with this PR and address it in a separate PR. That is, to make the "unsaved" status is affected correctly when we get new changes from "model from source" or "model with LLM". But just say if you'd prefer to delay this PR and wait for that fix first.
Checklist
ready-for-doc-reviewlabel there.